Update Rust crate ruma-common to 0.15.0 #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.13.0
->0.15.0
Release Notes
ruma/ruma (ruma-common)
v0.15.0
: ruma-common 0.15.0Compare Source
Breaking changes:
#[serde(flatten)]
on the only body field of a#[request]
or#[response]
struct is disallowed.#[ruma_api(body)]
must be used instead.Improvements:
ruma_identifiers_storage
compile-timecfg
setting can also be configured by setting theRUMA_IDENTIFIERS_STORAGE
environment variable at compile time. It has the benefit of not requiring to re-compile all the crates of the dependency chain when the value is changed.unstable-exhaustive-types
cargo feature was replaced by theruma_unstable_exhaustive_types
compile-timecfg
setting. Like allcfg
settings, it can be enabled at compile-time with theRUSTFLAGS
environment variable, or inside.cargo/config.toml
. It can also be enabled by setting theRUMA_UNSTABLE_EXHAUSTIVE_TYPES
environment variable.HttpPusherData
allows to set custom data for the pusher in thedata
field, due to a clarification in the spec.default_payload
field that was behind theunstable-unspecified
was removed. It can be added manually to the custom data.v0.14.1
: ruma-common 0.14.1Compare Source
Bug fixes:
KeyId::key_name
method now returns the key name. In 0.14.0,key_name
mistakenly returned the algorithm.v0.14.0
: ruma-common 0.14.0Compare Source
Bug fixes:
instance_id
field was removed fromProtocolInstanceInit
and is now anOption<String>
forProtocolInstance
. It made theunstable-unspecified
feature non-additive.Breaking changes:
query_map
attribute of therequest
macro toquery_all
, and remove the required bound to implementIntoIterator<Item = (String, String)>
. This allows to use a struct or enum as well as a map to represent the list of query parameters. Note that the (de)serialization of the type used must work withserde_html_form
.header
attribute for therequest
andresponse
macros accepts any type that implementsToString
andFromStr
.compat-key-id
cargo feature was renamed tocompat-server-signing-key-version
.(Owned)KeyName
was renamed to(Owned)ServerSigningKeyVersion
and is now validated according to the set of allowed characters defined in the docs, unless thecompat-server-signing-key-version
cargo feature is enabled.KeyId
changed. The algorithm part must implementKeyAlgorithm
and the key name part must implementKeyName
.(owned_)server_signing_key_id
macros were removed. For compile-time validated construction, useServerSigningKeyId::from_parts
with aSigningKeyAlgorithm
and theserver_signing_key_version
macro.Signatures::insert
toSignatures::insert_signature
.Signatures::insert
is now dereferenced toBTreeMap::insert
.DeviceKeyAlgorithm::SignedCurve25519
into the newOneTimeKeyAlgorithm
type.(Owned)CrossSigningKeyId
and use it instead ofOwnedDeviceKeyId
to identifyCrossSigningKey
'skeys
.(Owned)CrossSigningOrDeviceSigningKeyId
and use it instead ofOwnedDeviceKeyId
to identify signing keys inDeviceKeys
's andCrossSigningKey
'ssignatures
.OwnedDeviceSigningKeyId
instead ofOwnedDeviceKeyId
to identify signing keys inSignedKey
'ssignatures
.(Owned)DeviceKeyId
is now a type alias of(Owned)KeyId
.(owned_)device_key_id
macro, instead useDeviceKeyId::from_parts
.CrossSigningOrDeviceSignatures
for thesignatures
ofDeviceKeys
.SignedKeySignatures
and replace it withDeviceSignatures
.CrossSigningKeySignatures
and replace it withCrossSigningOrDeviceSignatures
.Improvements:
InvalidHeaderValue
variant to theDeserializationError
struct, for cases where we receive a HTTP header with an unexpected value.Eq
/Hash
/PartialEq
forThirdPartyIdentifier
, to check whether aThirdPartyIdentifier
has already been added by another user.MatrixVersion::V1_11
andMatrixVersion::V1_12
.AuthScheme
that sending an access token via a query parameter is deprecated, according to MSC4126 / Matrix 1.11.Eq
andPartialEq
forMetadata
api::error::MatrixErrorBody::NotJson
outside of this crate.Signatures
, by implementingDeref
andDerefMut
, as well asFrom
,Extend
andFromIterator
from a list of(entity, key_identifier, value)
tuples.(Owned)OneTimeKeyId
and(Owned)OneTimeKeyName
to identify one-time and fallback keys instead of using(Owned)DeviceKeyId
.(Owned)Base64PublicKey
and(Owned)Base64PublicKeyOrDeviceId
to identify cross-signing keys.(owned_)base_64_public_key
to construct a compile-time validated(Owned)Base64PublicKey
.Configuration
📅 Schedule: Branch creation - "after 8pm,before 6am" in timezone America/Los_Angeles, Automerge - "after 8pm,before 6am" in timezone America/Los_Angeles.
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.